70 research outputs found

    Enabling Personalized Composition and Adaptive Provisioning of Web Services

    Get PDF
    The proliferation of interconnected computing devices is fostering the emergence of environments where Web services made available to mobile users are a commodity. Unfortunately, inherent limitations of mobile devices still hinder the seamless access to Web services, and their use in supporting complex user activities. In this paper, we describe the design and implementation of a distributed, adaptive, and context-aware framework for personalized service composition and provisioning adapted to mobile users. Users specify their preferences by annotating existing process templates, leading to personalized service-based processes. To cater for the possibility of low bandwidth communication channels and frequent disconnections, an execution model is proposed whereby the responsibility of orchestrating personalized processes is spread across the participating services and user agents. In addition, the execution model is adaptive in the sense that the runtime environment is able to detect exceptions and react to them according to a set of rules

    Method Families Concept: Application to Decision-Making Methods

    No full text
    International audienceThe role of variability in Software engineering grows increasingly as it allows developing solutions that can be easily adapted to a specific context and reusing existing knowledge. In order to deal with variability in the method engineering (ME) domain, we suggest applying the notion of method families. Method components are organized as a method family, which is configured in the given situation into a method line. In this paper, we motivate the concept of method families by comparing the existing approaches of ME. We detail then the concept of method families and illustrate it with a family of decision-making (DM) methods that we call MADISE

    INTEROP deliverable DTG 6.2 : Method repository

    Get PDF
    This deliverable presents the INTEROP method chunks repository (MCR), its architecture and provided services. It includes the definition of a reusable method chunk, its structure, illustrated with examples of method chunks stored in the repository and guidelines for method chunks definition and characterisation covering tasks TG6.2 and TG6.3 of the work plan of the task group. The main result is the definition of the structure of the method chunk repository emphasizing the link to interoperability. Interoperability is a first-class concept in the structure of the method chunk repository. It not only characterizes method chunks, i.e. procedures to solve interoperability problems, but also interoperability cases, i.e. the presentation of actual problems involving interoperability issues. TG 6 has produced three MCR prototypes. Two experiments were undertaken using the Metis system and one using ConceptBase. The task group attended a two-day intense workshop on Metis. As a result, two experiments with Metis as platform for the method chunk repository are under way and reported in this deliverable. One is realizing the structure of the MCR as specified in this report. The other is an alternative approach that serves as a benchmark and is reported in the appendix. The ConceptBase prototype utilizes the metamodel presented in this deliverable. We have analysed three cases involving various aspects of interoperability. One case is about establishing a broker platform for insurance agents, the second about linking the information systems in the public utility sector, and the third case is establishing the relation of the ATHENA Model-Driven Interoperability Framework to the goals of the MCR. The results of the TG6 have been published at the ISD conference 2006 and the ER conference 2006. Copies of the papers are included in the appendix. The report of the example session with the method chunk repository has been shifted towards deliverable TG6.3 (Tutorial of the MCR). This is the more logical place. We want to emphasize that TG6 was not only busy in drafting concepts, exploring the state of the art, and analyzing cases. We are actually experimenting with a prototype and consider this a valuable contribution to the network. As soon as the prototype is stable, knowledge about interoperability solutions can be coded in this repository and can guide designers of interoperable systems by experience knowledge

    Decision-Making Ontology for Information System Engineering

    No full text
    International audienceInformation Systems (IS) engineering (ISE) processes contain steps where decisions must be made. Moreover, the growing role of IS in organizations involves requirements for ISE such as quality, cost and time. Considering these aspects implies that the number of researches dealing with decision-making (DM) in ISE increasingly grows. As DM becomes widespread in the ISE field, it is necessary to build a representation, shared between researchers and practitioners, of DM concepts and their relations with DM problems in ISE. In this paper, we present a DM ontology which aims at formalizing DM knowledge. Its goal is to enhance DM and to support DM activities in ISE. This ontology is illustrated within the requirements engineering field

    Process Patterns for Component-Based Software Development

    Full text link
    Abstract. Component-Based Development (CBD) has been broadly used in software development, as it enhances reusability and flexibility, and reduces the costs and risks involved in systems development. It has therefore spawned many widely-used approaches, such as Commercial Off-The-Shelf (COTS) and software product lines. On the other hand, in order to gain a competitive edge, organizations need to define custom processes tailored to fit their specific de-velopment requirements. This has led to the emergence of process patterns and Method Engineering approaches. We propose a set of process patterns commonly encountered in component-based development methodologies. Seven prominent component-based method-ologies have been selected and reviewed, and a set of high-level process patterns recurring in these methodologies have been identified. A generic process framework for component-based development has been proposed based on these process patterns. The process patterns and the generic framework can be used for developing or tailoring a process for producing component-based systems

    Cargo Cults in Information Systems Development: a Definition and an Analytical Framework

    Get PDF
    Organizations today adopt agile information systems development methods (ISDM), but many do not succeed with the adoption process and in achieving desired results. Systems developers sometimes fail in efficient use of ISDM, often due to a lack of understanding the fundamental intentions of the chosen method. In many cases organizations simply imitate the behavior of others without really understanding why. This conceptual paper defines this phenomenon as an ISDM cargo cult behavior and proposes an analytical framework to identify such situations. The concept of cargo cults originally comes from the field of social anthropology and has been used to explain irrational, ritualistic imitation of certain behavior. By defining and introducing the concept in the field of information systems development we provide a diagnostic tool to better understand one of the reasons why ISDM adoption sometimes fail

    How to Exploit the Digitalization Potential of Business Processes

    Get PDF
    Process improvement is the most value-adding activity in the business process management (BPM) lifecycle. Despite mature knowledge, many approaches have been criticized to lack guidance on how to put process improvement into practice. Given the variety of emerging digital technologies, organizations not only face a process improvement black box, but also high uncertainty regarding digital technologies. This paper thus proposes a method that supports organizations in exploiting the digitalization potential of their business processes. To achieve this, action design research and situational method engineering were adopted. Two design cycles involving practitioners (i.e., managers and BPM experts) and end-users (i.e., process owners and participants) were conducted. In the first cycle, the method’s alpha version was evaluated by interviewing practitioners from five organizations. In the second cycle, the beta version was evaluated via real-world case studies. In this paper, detailed results of one case study, which was conducted at a semiconductor manufacturer, are included

    Component-Based Method Development: An Experience Report

    No full text
    International audienceA method defines a systematic process for problem solving including the required aids and resources. This paper aims at contributing to the area of method development and in particular to practices and experiences in this field by reporting on a case from conceptual modelling and reflecting on lessons learned in it. The contributions of the paper are (1) an application case from method development in a distributed team, (2) the actual method development process integrating work procedure, cooperation principles and notation, and (3) experiences and lessons learned from developing a method component for context modeling

    Situational method engineering: Fragments or chunks?

    Full text link
    In Situational Method Engineering, the concepts of both fragment and chunk have been proposed as the atomic element. These are examined here in terms of their conceptual integrity and in terms of how they may be used in method construction, drawing parallels to show that the similarities are more than the differences. The new ISO/IEC 24744 standard metamodel is used as a conceptual framework to perform these mappings
    corecore